[PATCH 1/4] dnp3: check done state, not complete state for progress
authorJason Ish <jason.ish@oisf.net>
Tue, 6 Jan 2026 22:15:09 +0000 (16:15 -0600)
committerAndreas Dolp <dev@andreas-dolp.de>
Thu, 23 Apr 2026 05:14:21 +0000 (07:14 +0200)
commit4a6626fd3e4021a67ea670965e3b954b61331c8d
tree119ac376bbeb56c1737e73e6d88843b7f48ddc38
parent711d4662c141a0e419adddc5eab73a3a755ca680
[PATCH 1/4] dnp3: check done state, not complete state for progress

Complete is a flag used to tell if the message was completely parsed,
as not all messages may be completely parsed if we don't know all
their objects. However, they are still "done".

In the alstate-progress callback, check the done flag, not the
complete flag.

Ticket: #8181
(cherry picked from commit d61eef9a8a0d92921989479de15e5cbfec3251a9)

Origin: upstream, https://github.com/OISF/suricata/commit/63225d5f8ef64cc65164c0bb1800730842d54942.patch
Bug: https://redmine.openinfosecfoundation.org/issues/8181
Subject: Upstream fix for CVE-2026-22259 part 1

Gbp-Pq: Name CVE-2026-22259_1.patch
src/app-layer-dnp3.c